The vservers command node includes the following subnode commands:
routes
servers
Each of the subnode commands, and the leaf-node commands attached to them, is described in detail, with parameters and arguments listed for each command.
Examples of command usage are included in the discussions.
CLI:
vservers routes delete -vsname virtual_server_name -nexthop nexthop_IP_address -netnumber network_IP_address -netmask netmask
GUI: Navigate to the Virtual Servers → Routing node, then select the appropriate route from the table and run the Delete command from the drop-down menu of the action pane.
The vservers routes delete command identifies a virtual server by its virtual server name and removes its static route.
-vsname virtual_server_name
This is the name of the virtual server.
-nexthop nexthop_IP_address
This is the next-hop IP address.
-netnumber network_IP_address
This is the network IP address.
-netmask netmask
This is the network IP mask.
The following command example identifies a virtual server named Server1vserver1 and removes its route, which is defined as having a next-hop address of 10.1.1.104, a network address of 10.1.1.14, and a netmask of 255.255.255.0.
spinserver::> vservers routes delete -vsname Server1vserver1 -nexthop 10.1.1.104 -netnumber 10.1.1.14 -netmask 255.255.255.0
CLI:
vservers routes show [-vsname virtual_server_name -nexthop nexthop_IP_address -netnumber network_IP_address -netmask netmask]
GUI: Navigate to the Virtual Servers → Routing node. To display information about a specific route, select it from the table and run the Show command from the drop-down menu of the action pane.
The vservers routes show command displays routing information about one virtual server or all virtual servers. To display route information about one route, use the command with all the parameters. To display route configuration information about a list of routes in the system, do not use the parameters. If one parameter is used, all other parameters must be specified. The command displays the following information about the virtual server or virtual servers:
Virtual server name
Default gateway address
Network address
Network mask
Metric
[-vsname virtual_server_name]
This is the name of the virtual server. This parameter is optional; however, if it is used, all other parameters must also be specified.
[-nexthop nexthop_IP_address]
This is the next-hop IP address. This parameter is optional; however, if it is used, all other parameters must also be specified.
[-netnumber network_IP_address]
This is the network IP address. This parameter is optional; however, if it is used, all other parameters must also be specified.
[-netmask netmask]
This is the network IP mask. This parameter is optional; however, if it is used, all other parameters must also be specified.
The following command example displays route configuration information.
spinserver::> vservers routes show
Virtual Server Default Gateway Network Address Network Mask Metric
Address
Server1 10.3.0.3 0.0.0.0 0.0.0.0 1
The vservers servers subnode includes the following leaf-node commands:
adddefaultgateway
addstaticroute
bindif
delete
modify
new
newrootmirror
offline
online
show
unbindif
CLI:
vservers servers adddefaultgateway -vsname virtual_server_name -gateway gateway_IP_address
GUI: Navigate to the Virtual Servers → Servers node, then select the appropriate server from the table and run the Add Default Gateway command from the drop-down menu of the action pane. Enter the appropriate values into the table that is displayed, then click Add Default Gateway.
The vservers servers adddefaultgateway command adds a default gateway to a virtual server.
-vsname virtual_server_name
This is the name of the virtual server.
-gateway gateway_IP_address
This is the gateway IP address.
The following command example adds a gateway IP address of 10.1.1.104 to a virtual server named Server1vserver1.
spinserver::> vservers servers adddefaultgateway -vsname Server1vserver1 -gateway 10.1.1.104
CLI:
vservers servers addstaticroute -vsname virtual_server_name -gateway gateway_IP_address -netaddress network_IP_address -netmask netmask -metric metric
GUI: Navigate to the Virtual Servers → Servers node, then select a virtual server from the table that is displayed and run the Add Static Route command from the drop-down menu of the action pane. Enter the appropriate values into the table that is displayed, then click Add Static Route.
The vservers servers addstaticroute command creates a static route for a virtual server.
-vsname virtual_server_name
This is the name of the virtual server.
-gateway gateway_IP_address
This is the gateway IP address.
-netaddress network_IP_address
This is the network IP address.
-netmask netmask
This is the network IP mask.
-metric metric
This is the most economical route.
The following command example adds a new static route to a virtual server named Server1vserver1. The route is defined with a gateway IP address of 10.1.1.104, a destination IP address of 10.1.1.14, a netmask of 255.255.255.0, and a metric of 1.
spinserver::> vservers servers addstaticroute -vsname Server1vserver1 -gateway 10.1.1.104 -netaddress 10.1.1.14 -netmask 255.255.255.0 -metric 1
CLI:
vservers servers bindif -vsname virtual_server_name -ssid spinserver -ifname interface_name
GUI: Navigate to the Virtual Servers → Servers node, then select the appropriate server from the table and run the Bind Network Interface command from the drop-down menu of the action pane. Enter the appropriate values into the table that is displayed, then click Bind Network Interface.
The vservers servers bindif command identifies a interface by its SpinServer and interface name and binds the virtual interface to a virtual server.
-vsname virtual_server_name
This is the name of the virtual server.
-ssid spinserver
This is name of the SpinServer.
-ifname interface_name
This is the name given to the interface.
The following command example identifies a virtual server named Server1vserver1 on a SpinServer named Server1 and binds a virtual interface named Server1interface1 to it.
spinserver::> vservers servers bindif -vsname Server1vserver1 -ssid Server1 -ifname Server1interface1
CLI:
vservers servers delete -vsname virtual_server_name
GUI: Navigate to the Virtual Servers → Servers node, then select the appropriate server from the table and run the Delete command from the drop-down menu of the action pane.
The vservers server delete command identifies a virtual server by its name and removes it from the network.
Note: Using the vservers servers delete command deletes all the virtual file systems associated with the virtual server, the network interfaces, and the virtual server itself.
Important: You cannot undo the deletion of virtual file systems, network interfaces, and virtual servers.
The following command example identifies a virtual server named Server1vserver1 and removes it from the network.
spinserver::> vservers servers delete -vsname Server1vserver1
CLI:
vservers servers modify -vsname virtual_server_name [-spinauth {true | false}] [-floatingsuperuser {true | false}] [-minauth minimum_authentication] [-rulesetname rule_set_name] [-virusscanrwvfs {true | false}] [-virusscanrovfs {true | false}] [-showspinshot {true | false}] [-restrictedacl {true | false}]
GUI: Navigate to the Virtual Servers → Servers node, then select the appropriate server from the table and run the Show command from the drop-down menu of the action pane. Make the appropriate changes in the table that is displayed, then run the Modify command from the drop-down menu.
The vservers servers modify command identifies a virtual server by its name and modifies its minimum authentication level.
-vsname virtual_server_name
This is the name of the virtual server.
[-spinauth {true | false}]
This specifies whether the SpinAuth authentication mechanism is used on the virtual server. The default is false.
[-floatingsuperuser {true | false}]
This specifies whether the virtual server permits a floating superuser. The default is false.
[-minauth minimum_authentication]
This is the minimum authentication level for the virtual server. Possible values are none, cifs-ntlm, cifs-kerberos, and nfs-kerberos.
[-rulesetname rule_set_name]
This specifies the name of a rule set that is to be applied to the virtual server.
[-virusscanrwvfs {true | false}]
This specifies whether virus scanning is enabled on read-write VFSs. The default is false.
[-virusscanrovfs {true | false}]
This specifies whether virus scanning is enabled on read-only VFSs. The default is false.
[-showspinshot {true | false}]
This specifies whether .spinshot directories on the virtual server are visible to clients. The default is false.
[-restrictedacl {true | false}]
This specifies whether CIFS ACLs are used (false) or not used (true) on files on any VFSs that are created on the virtual server. The default is false (that is, ACLs are used). If CIFS ACLs are not used, UNIX mode bits are the only permissions set on files on the VFS, and attempting to modify ACLs from a CIFS client results only in changes to the mode bits.
The following command example identifies a virtual server named Server1vserver1 and changes its minimum authentication level to nfs-kerberos.
spinserver::> vservers servers modify -vsname Server1vserver1 -minauth nfs-kerberos
CLI:
vservers servers new -vsname virtual_server_name -spdevid storage_pool_ID -spinauth {true | false} -floatingsuperuser {true | false} -minauth minimum_authentication -rulesetname rule_set_name -virusscanrwvfs {true | false} -virusscanrovfs {true | false} -showspinshot {true | false} -restrictedacl {true | false}
GUI: Navigate to the Virtual Servers → Servers node, then click New in the top bar of the action pane. Enter the appropriate values into the table that is displayed, then click Create.
The vservers servers new command creates a virtual server and identifies it by its virtual server name and the name of the storage pool to which it is attached.
-vsname virtual_server_name
This is the name of the virtual server.
-spdevid storage_pool_ID
This is the ID of the storage pool.
-spinauth {true | false}
This specifies whether the SpinAuth authentication mechanism is used on the virtual server. The default is false.
-floatingsuperuser {true | false}
This specifies whether the virtual server permits a floating superuser. The default is false.
-minauth minimum_authentication
This is the minimum authentication level for the virtual server. Possible values are none, cifs-ntlm, cifs-kerberos, and nfs-kerberos.
-rulesetname rule_set_name
This specifies the name of a rule set that is to be applied to the virtual server.
-virusscanrwvfs {true | false}
This specifies whether virus scanning is enabled by default on read-write VFSs. The default is false.
-virusscanrovfs {true | false}
This specifies whether virus scanning is enabled by default on read-only VFSs. The default is false.
-showspinshot {true | false}
This specifies whether .spinshot directories on the virtual server are visible to clients. The default is false.
-restrictedacl {true | false}
This specifies whether CIFS ACLs are used (false) or not used (true) on files on any VFSs that are created on the virtual server. The default is false (that is, ACLs are used). If CIFS ACLs are not used, UNIX mode bits are the only permissions set on files on the VFS, and attempting to modify ACLs from a CIFS client results only in changes to the mode bits.
The following command example creates a new virtual server named Server1vserver1 and attaches it to a storage pool named Server1pool1. The virtual server does not use SpinAuth or permit a floating superuser. The minimum authentication level is specified as nfs-kerberos. A rule set named default_rules is applied to the virtual server. Virus scanning is enabled by default on read-write VFSs but not on read-only VFSs. All .spinshot directories on the virtual server are visible to clients. CIFS ACLs are used on files on new VFSs created on the virtual server.
spinserver::> vservers servers new -vsname Server1vserver1 -spdevid Server1pool1 -spinauth false -floatingsuperuser false -minauth nfs-kerberos -virusscanrwvfs true -virusscanrovfs false -showspinshot true -restrictedacl false
CLI:
vservers servers newrootmirror -vsname virtual_server_name -sinkvfs sink_VFS_name -sinksp sink_storage_pool
GUI: Navigate to the Virtual Servers → Servers node, then select the appropriate virtual server from the table and run the New Root Mirror command from the drop-down menu of the action pane. Enter the appropriate values into the table that is displayed, then click New Root Mirror.
The vservers servers newrootmirror command creates a backup of a virtual server's root. Unlike other mirror commands, this command does not require the SpinMirror software package.
-vsname virtual_server_name
This is the name of the virtual server whose root is to be mirrored.
-sinkvfs sink_VFS_name
This is the VFS into which the root is to be mirrored.
-sinksp sink_storage_pool
This is the storage pool on which the sink VFS is located.
The following command example mirrors the root of a virtual server named vs0. The root is mirrored to a VFS named repos_vfs_1 on a storage pool named sp2.
spinserver::> vservers servers newrootmirror -vsname vs0 -sinkvfs repos_vfs_1 -sinksp sp2
CLI:
vservers servers offline -vsname virtual_server_name
GUI: Navigate to the Virtual Servers → Servers node, then select the appropriate server from the table and run the Offline command from the drop-down menu of the action pane.
The vservers servers offline command identifies a virtual server and takes offline all virtual interfaces bound to it.
-vsname virtual_server_name
This is the name of the virtual server whose virtual interfaces are taken offline.
The following command example identifies a virtual server named Server1vserver1 and takes offline all virtual interfaces bound to it.
spinserver::> vservers servers offline -vsname Server1vserver1
CLI:
vservers servers online -vsname virtual_server_name
GUI: Navigate to the Virtual Servers → Servers node, then select the appropriate server from the table that is displayed and run the Online command from the drop-down menu of the action pane.
The vservers servers online command identifies a virtual server and brings online all virtual interfaces bound to it.
-vsname virtual_server_name
This is the name of the virtual server whose virtual interfaces are brought online.
The following command example identifies a virtual server named Server1vserver1 and brings online all virtual interfaces bound to it.
spinserver::> vservers servers online -vsname Server1vserver1
CLI:
vservers servers show [-vsname virtual_server_name]
GUI: Navigate to the Virtual Servers → Servers node. To display information about a specific server, select it from the table and run the Show command from the drop-down menu of the action pane.
The vservers servers show command displays information about one virtual server or all virtual servers. To display information about one virtual server, use the command with the -vsname parameter. To display configuration information about all of the virtual servers in the system, do not use the -vsname parameter. The command displays the following information:
Virtual server name
Network interface name
Minimum authentication level
Whether SpinAuth is enabled
Whether floating superusers are enabled
The following additional information is displayed about a specific virtual server:
Storage pool for root VFS
User type for root FID
Domain of root FID
User of root FID
Group of root FID
Virtual server ID
ID of root VFS
Status
Name of the export rule set
Whether virus scanning is enabled by default for read-write VFSs on the virtual server
Whether virus scanning is enabled by default for read-only VFSs on the virtual server
[-vsname virtual_server_name]
This is the name of the virtual server whose configuration information is displayed by the system.
The following example displays information about all virtual servers:
spinserver::> vservers servers show
Name Network Interface Min Authentication
(NFS Only)
Server1 Server12:Data, Server1:Data none
The following example identifies a virtual server named vs0 and displays its configuration information.
spinserver::> vservers servers show -vsname vs0 Name vs0 Storage Pool for Root VFS pool0 User Type for root FID NFS Domain of root FID example.com User of root FID 0 Group of root FID 0 Network Interfaces Server12:Data, Server:Data Virtual Server ID 15 Root VFS ID 5369 Status online (Data,Data) Min Authentication none Min Authentication nfs-kerberos Export Ruleset Name default_ruleset VirusScan for R-W VFS true VirusScan for R-O VFS true
CLI:
vservers servers unbindif -vsname virtual_server_name -ssid spinserver -ifname interface_name
GUI: Navigate to the Virtual Servers → Servers node, then select the appropriate server from the table and run the Unbind Network Interface command from the drop-down menu of the action pane.
The vservers servers unbindif command identifies a interface by its server and interface name and unbinds a virtual interface from a virtual server.
Copyright © 2004 Network Appliance, Inc.; copyright © 2003, 2004 Spinnaker Networks, LLC. All rights reserved. Specifications subject to change without notice.